Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1809

reference: 273-tree-1
name: 1809
tree-preservation-order: undefined
273-tpo-1
uprn
address-text
point: POINT (-0.979211 50.858670)
geometry: MULTIPOLYGON (((-0.979112 50.858660,-0.979116 50.858679,-0.979130 50.858697,-0.979152 50.858711,-0.979179 50.858720,-0.979210 50.858724,-0.979241 50.858721,-0.979268 50.858712,-0.979291 50.858698,-0.979305 50.858681,-0.979311 50.858662,-0.979306 50.858642,-0.979292 50.858624,-0.979271 50.858610,-0.979243 50.858601,-0.979212 50.858598,-0.979182 50.858601,-0.979154 50.858609,-0.979131 50.858623,-0.979117 50.858640,-0.979112 50.858660)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL